Telecom business-oriented taxonomy for reusable services

ABSTRACT

A method, system, and computer program product for a management and development framework of shared business service assets within a common services oriented architecture strategy are provided. The framework comprises a multi-dimensional business oriented taxonomy that is aligned with organizational business services requiring software support. The framework affords advantageous placement of business service assets using a product publication schema and rapid search and discovery of business service assets through a product discovery schema. Implementation of the framework across multiple units of an organization facilitates business service asset reuse, thereby enabling a minimization of asset redundancy, reduction in business application development time and cost, and rapid market entry for organizational products.

BACKGROUND

Software development for organizations is traditionally carried outproduct-by-product with applications developed to address specificproduct and service needs. As a result organizations develop largelibraries of custom applications targeted at particular businesssolutions. To manage these large libraries, companies resort tocataloging their software using metadata identifiers, such as author,date of creation, etc. These library systems enable companies toassociate desirable attributes with an application. Depending on theattribute selected for association, applications directed to similarsubject matter may be identified with differing attributes. Aconsequence of this structure is repetitive and redundant softwareapplications within the same organization. Further, should a developerwish to search the library for a particular application, knowledge ofthe metadata attributes associated with the application must be known inorder to effectively retrieve the application. Additionally, use ofmetadata is limited in its ability to distinguish the purpose and orbusiness value of any particular application. Metadata does not helpdetermine the relationship between different applications, nor does itshed light on an application's applicability in a specific businessprocessing area or context. Thus, organizations accumulate a plethora ofsoftware services with no efficient awareness of an application'slocation nor the function it provides.

Recent empirical studies indicate that software programs directed tocore business functions can be implemented as many as 30 times acrossdifferent applications. This represents tremendous inefficiency and costboth in development and maintenance of these redundant systems.Accordingly, what is needed is an efficient tool to assist developersand users of software assets that enables rapid search and retrieval ofbusiness software solutions, while providing a platform to minimizeredundancy.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying figures depict certain illustrative embodiments and mayaid in understanding the following detailed description. The embodimentsdepicted are to be understood as exemplary and in no way limiting of theoverall scope of the invention. The detailed description will makereference to the following figures, in which:

FIG. 1 is a flow chart illustrating the process flow of publishing anddiscovering business service assets in accordance with an exemplaryembodiment.

FIG. 2 illustrates an example network in which embodiments of thepresent system, method and computer program product may be practiced.

FIG. 3 illustrates an exemplary interface for publishing businessservice assets.

FIG. 4 illustrates an exemplary interface for discovering businessservice assets.

Throughout the drawings, like reference numbers refer to like elements,features, and structures.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The matters exemplified in this description are provided to assist in acomprehensive understanding of various exemplary embodiments disclosedwith reference to the accompanying figures. Accordingly, those ofordinary skill in the art will recognize that various changes andmodifications of the exemplary embodiments described herein can be madewithout departing from the spirit and scope of the claimed invention.Descriptions of well-known functions and constructions are omitted forclarity and conciseness.

A large library of reusable software components, notably businessservice assets, requires a cataloging structure that is both alignedwith an organization's business needs, and provides a proper frameworkto enable convenient discovery and reuse of assets when constructing newbusiness systems. Such a system should be operable by non-technicalpersonnel, such as business analysts, and new developers who may betechnically competent but lack the organizational exposure to adequatelyunderstand the inner-workings of the company. Accordingly, the presentdisclosure encompasses a software solution that (a) classifies new andexisting business assets; (b) facilitates locating assets that meetspecific business requirements; and (c) enables reuse of business assetsacross organizational strategic business units, company partners, andthird-party content providers.

Previous attempts at forming a cataloging structure were not developedwith the aim of advantageous product positioning to facilitate rapiddiscovery and usage in a business-specific context. Accordingly, onefocus of the present disclosure is to establish a product and serviceclassification superstructure that helps developers (and asset “owners”)properly position their products for easy discovery when users aresearching for assets that are most likely to satisfy their specificobjectives. As used herein, an asset or product's position refers to howusers view the product within a given market, whether that market beinternal or external. A “user” can be a human operator or an authorizedapplication, that is, a subscribing program operating automatically withor without human intervention. Usage of an asset can be real-time orotherwise.

The present disclosure provides a classification superstructure thataffords a dynamic and flexible implementation which does not impose arigid standard or specific structure on the underlying published servicefor asset use/reuse. Assets are orchestrated to enable a high-levelunderstanding of the relationship between categories, and may standalone as specific components directed to a specific business solutionrather than a monolithic dedicated application. The dedicated focus ofsome assets enables highly efficient operations, which aids in speed ofdevelopment and time to market, that is, faster and more economicdelivery of systems.

Experience suggests that most routinely performed important businesstransactions or functions number on the order of 500. Such transactionsinclude, for example, retrieving customer information and verifyingcustomer credit history. Accordingly, the software solution of thisdisclosure presents a unique multi-dimensional Telecom-specific businessoriented taxonomy for use as a high-level classification scheme for adynamic inventory of new and existing Common Business Service (CBS)components. The taxonomy comprises a Management Area, that is, a Processorientation, an Object Type, that is, a Payload orientation; and aService Line, that is, a Product orientation. Because of the dynamicnature of the taxonomy, it can support and accommodate a high degree ofservice sharing and service independence, and can span all lines ofbusiness units within the organization, products, and IT assets andservices.

The Process orientation is a high-level generic business functionclassification that is independent of the object types or service linesupported. The Payload orientation is a general reference to the typesof business objects exchanged in a service payload. The Productorientation is an organizational business product or service linesupported by the framework of this software solution. Each orientationforms a dimension within the taxonomy. This taxonomy is business goalfocused and each of the three identified dimensions includes a list ofpermissible categories that are process and product oriented. Thecategories can be extended over time and additional dimensions added asorganizational needs require. This disclosure, however, will focus onthe above three business-oriented dimensions of the taxonomy forpurposes of explanation, but the invention is not limited to thisquantity or categories.

Users can both publish and discover business service assets. Publishinginvolves a process under which software assets are registered with theframework and made available for search and use. Publishing enables aparticular software asset to be located within the framework via usersearch, that is, discovery and thereby enables use of the asset within abusiness solution or application under development. Software assets arepublished according to criteria set out below. Published assets can bereused time and again.

Discovering involves a process whereby business service assets aresearched for and located. Business service assets located via thediscovery process are identified by an instance of the asset. That is,the physical program code of the asset remains local to the platformwhere it operates, such as, for example, a Java run-time environmentsand a logical link or address is returned to enable asset use. Businessservice assets are discovered according to criteria set out below. Oneadvantage of using an instance is that changes or upgrades can be madeto an asset and the change will be implemented immediately throughoutthe network, as opposed to having to push the upgrade to affectedsystems. Discovering may return instances to multiple assets from whicha user can choose. Users may wish to consider management data associatedwith an asset to inform their selection. Management data includesinformation about the asset such as ownership, frequency of usesoccurrence of failure, etc.

Service providers, that is, publishers, are users who seek to publish aparticular business service asset to the framework. They are required toidentify at least one category within at least one dimension of thetaxonomy so as to associate the asset with the category and therebyfacilitate future search. The association of asset and category shouldbe in alignment with a particular business solution or strategy of theorganization. In one exemplar implementation, however, publishers arerequired to identify at least one category in each dimension of thetaxonomy.

Potential subscribers, that is, discoverers, are users who seek tolocate a business service asset published within the framework. Tolocate an asset, discovers must identify at least one category within atleast one dimension of the taxonomy so as to associate the asset withthe category, then execute a search. As with publishing, the associationof asset and category should be in alignment with a particular businesssolution or strategy of the organization. Discoverers use assets theylocate to create software applications directed to a business solutionor strategy. By locating and reusing existing business service assets,discoverers are relieved from having to “re-develop” assets from scratchand create wasteful redundancy. Reuse of existing software assetsresults in significant time and cost savings.

As discussed above, the multi-dimensional business process-orientedtaxonomy presented herein addresses three dimensions: a processdimension, a payload dimension, and a product dimension. Each dimensionof the taxonomy comprises one or more categories representative oforganizational processes and services. Collectively, the categoriesaddress the majority of important business transactions or functionsthat are routinely performed within an organization. Such transactionsinclude, for example, retrieving customer information and verifyingcustomer credit history. When publishing or discovering, users willassociate a particular business service asset with one or morecategories in the dimensions to best assure that the asset is inalignment with the organization's goals and strategies.

By way of example, the following categories are illustrative of the typeof categories that occur within the taxonomy. The categories are dynamicand may expand and contract to meet organizational needs. Accordinglythe following list is an exemplary embodiment and should not beconstrued as finite or limiting.

Representative categories in the process dimension include:

-   -   Pre-Order and Sales Order Management;    -   Product, Pricing, Inventory Management;    -   Supplier, Partner Management;    -   Provisioning, Activation, Field Fulfillment Management;    -   Financial and Asset Management;    -   Customer, Workforce Management;    -   Device, Element Management;    -   Trouble, Test, Fault, Measurement Management    -   Billing, Payment, Mediation, Fraud, Credit Management;    -   Communication Process Management—Transmission, Routing        Signaling, Switching State/Session; and    -   General, Middleware Management—Distribution, Performance,        Security Logging, Alarms.

Representative categories in the payload dimension include:

-   -   Quotation;    -   Order or Service Request;    -   Order Status (includes Fulfillment, Acknowledgment);    -   Network Service Record;    -   Customer Service Record;    -   Work Order;    -   Credit Status;    -   Bill (includes Invoice);    -   Payment;    -   Usage;    -   Trouble Ticket;    -   Circuit Detail;    -   Product;    -   Receipt;    -   Person (workforce or customer identity);    -   Equipment;    -   Document (Standard MIME types exchanged in payload); and    -   Request (transaction, process).

Representative categories in the product dimension include:

-   -   Local Services;    -   Access Services;    -   Long Distance Services;    -   DSL Services;    -   Broadband/Optical Transport Services;    -   Video/Gaming Services;    -   Centrex and PBX Services;    -   Internet Services;    -   Equipment Services (CPE/Switches/Parts)    -   Directory Services;    -   Convergence and Collaboration Services;    -   VOIP Services;    -   Content Storage and Distribution Services (Email, Fax, Pager,        File Transfer, etc.);    -   Wireless Services;    -   Security Se ices; and    -   Special Services.

FIG. 1 is a flow chart illustrating the process flow of publishing anddiscovering business service assets in accordance with an exemplaryembodiment. A multi-dimensional business process-oriented taxonomy isprovided within a framework, step 100. The taxonomy comprises one ormore business service categories within multiple dimensions, which fordiscussion here comprise a process dimension, a payload dimension, and aproduct dimension. The categories are representative of organizationalprocesses and services, and collectively address the majority ofimportant business transactions or functions that are routinelyperformed within an organization. Such transactions include, forexample, retrieving customer information and verifying customer credithistory.

When publishing a business service asset, a user, that is, publisher,furnishes the asset they wish to publish, step 125, and selects one ormore business service categories to associate with the asset, step 135.The categories are selected so that the categories and asset with whichthey are to associate are in alignment with a particular businesssolution or goals and strategies of the organization. The asset is thenscreened to ensure that it meets organizational criteria, such asquality, and if the asset qualifies it is published within theframework, step 145. An acknowledgment is sent to the user/publisherinforming that the asset has been published or denied, step 155.

When discovering a business service asset, a user, that is, discoverer,selects one or more business service categories that are in alignmentwith the type of business service asset they seek to locate, step 120.As with publishing, the association of asset and category should be inalignment with a particular business solution or strategy of theorganization. The discoverer determines which categories are selectedbased on criteria for the design of the business process applicationbeing developed and for which the located business service assets are tosupport. For example, discoverers needing to develop an applicationsupporting customer enrollment in a new telecommunication program willwant to discover business service assets that are related to creditverification, order history, payment history, usage level, etc. Thediscoverer then selects business service categories that will likelylocate the relevant assets. Using the superstructure presented in thisdisclosure, discoverers can easily browse and search using the businessservice categories to enable them to select, collect, and orchestratethe appropriate services to meet a particular business process need, aswell as the integration requirements of applications they construct.

After selecting the appropriate categories, a discoverer then executes asearch to locate business service assets, step 130. To locate assets,one or more databases that store business service assets are accessed,and assets corresponding to the selected categories are identified. Aninstance of each located asset is returned to the discoverer forevaluation and selection, step 140. Additional criteria, such asmanagement data, can inform the discoverers selection. Management dataincludes information such as asset ownership, usage volume, failurerate, etc. Assets can be selected from different environments across thecomputing architecture, that is, for example, environments such as .Netand J2EE. Thus, discoverers are insulated from low level criteria suchas programming platform or development environment, and can then focuson selecting service assets based on relationships to core businessprocesses and business objectives.

For each located asset that has been selected, the discoverer enters aworkflow negotiation with the owner of the asset so that the asset canbe used within the application, step 150. The business processapplication is then developed accordingly.

FIG. 2 illustrates an example network in which embodiments of thepresent system, method and computer program product may be practiced.One or more database systems 230 . . . 230 n house business serviceasset information that has been published or otherwise prepared for useby the framework and is accessible to discoverers, where n designatesthe last of a plurality representing the number systems employed.Database systems 230 . . . 230 n comprise computer data structuresstored in computer memory such that a computer can manipulate the datastructures to access the business service assets or their logicalequivalents, such as pointers. The database systems 230 . . . 230 n maybe contained within their own discrete computer or, alternatively,located within one or more server computers 220 . . . 220 n, or evenwithin one or more of the user computers 210 . . . 210 n. The one ormore server computers communicate with the at least one database system230 . . . 230 n through the network 200. As with database systems 230 .. . 230 n, n designates the last of a plurality representing the numbersystems employed. Users can access the database systems 230 . . . 230 neither directly or through servers 220 . . . 220 n.

In an exemplary embodiment, one or more servers 220 . . . 220 n house acomputer program product for causing publishing and discovering ofbusiness service assets in a network 200. Although shown as a discreteunit in FIG. 2, exemplary embodiments provide network 200 asencompassing one or more of database systems 230 . . . 230 n, servers220 . . . 220 n and user computers 210 . . . 210 n. The computer programproduct comprises computer readable program code for structuring aframework that includes a multi-dimensional business process-orientedtaxonomy, code for business service asset publishing, and code forbusiness service asset discovering. The computer program product can beconfigured to operate on one or more server computers 220 . . . 220 n,and one or more user computers 210 . . . 210 n, The publishing anddiscovering are performed in accordance with the process described inthe discussion of FIG. 1 above.

In another exemplary embodiment, the network system of FIG. 2 furthercomprises an interface. The interface is operable on one or more usercomputers and at least one server computer. The interface comprisesreceiving from a publisher a business service asset with a request forpublication of the asset and selection of one or more business servicecategories in alignment with the asset, the business service categoriesforming a multi-dimensional business process-oriented taxonomy within aframework. The interface additionally includes qualifying the businessservice asset in response to the request for publication, and, ifqualified, publishing the asset. The interface further includesreturning to the publisher acknowledgment that the business serviceasset has been published or denied, and, for discovering a businessservice asset, receiving from a discoverer a selection of one or morebusiness service categories forming a multi-dimensional businessprocess-oriented taxonomy within a framework, and a request to locatebusiness service assets in alignment with the selected categories. Theinterface also comprises returning to the discoverer an instance of eachbusiness service asset located, wherein the dimensions of the taxonomycomprise a process dimension, a payload dimension, and a productdimension. The interface can be web-based. The interface can comprise aprogram-to-program interface or a graphical user interface (GUI).

As discussed, certain exemplary embodiments can be written ascomputer-readable code/instructions/programs and can be implemented indigital computers that execute the code/instructions/programs using acomputer readable medium. Examples of a computer readable medium includemagnetic storage media (for example, ROM, floppy disks, hard disks,among others), random-access memory (RAM), optical recording media forexample, CD-ROMs, or DVDs), and storage media such as carrier waves (forexample, transmission through the Internet). The computer readablemedium can also be distributed over network coupled computer systems sothat the computer readable code/instructions/programs is stored andexecuted in a distributed fashion. Further, functional programs, code,and code segments for accomplishing exemplary embodiments can be easilyconstrued by programmers of ordinary skill.

FIG. 3 illustrates an exemplary interface for publishing businessservice assets. In the exemplary embodiment illustrated in FIG. 3, onedimension of the multi-dimensional business process-oriented taxonomy isidentified as Process Management 310, a second dimension is identifiedas Object Type 320, and a third dimension is identified as Service Line330. Each dimension is shown having a selection window wherein businessservice categories representative of organizational processes andservices are displayed.

To select a category for publishing, users identify the desired categoryusing a pointing device, such as a mouse, then select the right-orientedarrow 301 to move the category to the appropriate selection window 310a, 320 a, and 330 a. This process can be repeated until all desiredcategories have been selected. If the majority, or perhaps all,categories are to be selected, the right-oriented double arrow 302 canbe used. To de-select a category, the left-oriented arrows 303, 304 areemployed. Slider 305 is used to move up and down within the categorydisplays.

FIG. 4 illustrates an exemplary interface for discovering businessservice assets. In the exemplary embodiment illustrated in FIG. 4, aswith FIG. 3, one dimension of the multi-dimensional businessprocess-oriented taxonomy is identified as Process Management 310, asecond dimension is identified as Object Type 320, and a third dimensionis identified as Service Line 330. Each dimension is shown having aselection window wherein business service categories representative oforganizational processes and services are displayed.

To select a category for discovery, users identify the desired categoryusing a pointing device, such as a mouse. Then, when all desiredcategories have been selected, users select Search 460. Management datain the form of Service Info 440 and Business Info 450 can be provided tofurther refine the business service asset search.

While the present invention has been particularly shown and describedwith reference to certain exemplary embodiments thereof, it will beunderstood by those of ordinary skill in the art that various changes inform and detail may be made therein without departing from the spiritand scope of the present invention as defined by the appended claims andequivalents thereof.

What is claimed is:
 1. A computer program product comprising anon-transitory computer readable medium having stored thereon computerreadable code for causing publishing and discovering of business serviceassets in a network, the computer readable program code comprising:computer readable program code for structuring a framework comprising amulti-dimensional business process-oriented taxonomy, the taxonomycomprising one or more business service categories within at least onedimension selected from a group consisting of: a process dimension, apayload dimension, and a product dimension; computer readable programcode for publishing a business service asset to the framework, thepublishing being responsive to: a first user selecting from within aninterface at least one of the one or more business service categories toassociate with the business service asset, and a second user screeningthe business service asset to ensure that the business service assetmeets organizational criteria; and computer readable program code fordiscovering the business service asset within the framework, thediscovering being responsive to a third user's selection of the at leastone of the one or more business service categories within the at leastone dimension of the multi-dimensional business process-orientedtaxonomy, the business service categories being in alignment with thebusiness service asset.
 2. The computer readable program code of claim1, wherein the code for business service asset publishing comprises:computer readable program code for detecting the selection of the atleast one of the one or more business service categories; and computerreadable program code for processing a business service asset inaccordance with the business service categories detected.
 3. Thecomputer readable program code of claim 1, wherein the code for businessservice asset discovering comprises: computer readable program code fordetecting the selection of the at least one of the one or more businessservice categories; and computer readable program code for locating abusiness service asset in accordance with the business servicecategories detected.
 4. The computer readable program code of claim 3,wherein the code for locating a business service asset comprises:computer readable program code for accessing a database comprisingpublished business service assets; computer readable program code forlocating within the database one or more business service assetscorresponding to the selected at least one of the one or more of thebusiness service categories; and computer readable program code forreturning an instance of each located business service asset to theframework.
 5. The computer readable program code of claim 4, furthercomprising computer readable program code for negotiating a workflowwith an owner of the located business service asset to facilitate assetuse.
 6. The computer readable program code of claim 5, wherein asset usecomprises developing a business process application.
 7. The computerreadable program code of claim 3, wherein the code for locating abusiness service asset further comprises computer readable program codefor processing management data associated with the business serviceasset, the management data comprising asset ownership, usage volume, andfailure rate.
 8. The computer readable program code of claim 1, whereinthe process dimension comprises one or more categories from a setcomprising: Pre-Order and Sales Order Management; Product, Pricing,Inventory Management; Supplier, Partner Management; Provisioning,Activation, Field Fulfillment Management; Financial and AssetManagement; Customer, Workforce Management; Device, Element Management;Trouble, Test, Fault, Measurement Management Billing, Payment,Mediation, Fraud, Credit Management; Communication ProcessManagement—Transmission, Routing, Signaling, Switching, State/Session;and General, Middleware Management—Distribution, Performance, Security,Logging, Alarms; wherein the payload dimension comprises one or morecategories from the set comprising: Quotation; Order or Service Request;Order Status (includes Fulfillment, Acknowledgement); Network ServiceRecord; Customer Service Record; Work Order; Credit Status; Bill(includes Invoice); Payment; Usage; Trouble Ticket; Circuit Detail;Product; Receipt; Person (workforce or customer identity); Equipment;Document (Standard MIME types exchanged in payload); and Request(transaction, process); wherein the product dimension comprises one ormore categories from the set comprising: Local Services; AccessServices; Long Distance Services; DSL Services; Broadband/OpticalTransport Services; Video/Gaming Services; Centrex and PBX Services;Internet Services; Equipment Services (CPE/Switches/Parts) DirectoryServices; Convergence and Collaboration Services; VOIP Services; ContentStorage and Distribution Services (Email, Fax, Pager, File Transfer,etc.); Wireless Services; Security Services; and Special Services.
 9. Acomputer implemented method for publishing and discovering businessservice assets in a network, the method comprising: providing amulti-dimensional business process-oriented taxonomy within a framework,the taxonomy comprising one or more business service categories within aprocess dimension, a payload dimension, and a product dimension; forpublishing a business service asset to the framework: a first userproviding a business service asset and selecting at least one of the oneor more of the business service categories in alignment with thebusiness service asset within at least one dimension of themulti-dimensional business process-oriented taxonomy, a second userscreening the business service asset provided by the first user toensure that the business service asset provided by the first user meetsorganizational criteria; and executing publication of the businessservice asset to the framework using a computer processor; and fordiscovering the business service asset, receiving a third user'sselection of the at least one of the one or more of the business servicecategories within the at least one dimension of the multi-dimensionalbusiness process-oriented taxonomy and executing a search to locate thebusiness service asset in alignment with the selected one or more of thebusiness service categories.
 10. The method of claim 9, wherein thesearch comprises: accessing a database comprising published businessservice assets; locating within the database one or more businessservice assets corresponding to the selected one or more the businessservice categories; and returning an instance of each located businessservice asset to the framework.
 11. The method of claim 10, furthercomprising negotiating a workflow with an owner of the located businessservice asset to facilitate asset use.
 12. The method of claim 9,wherein the search is further refined by specifying management dataassociated with the business service asset, the management datacomprising asset ownership, usage volume, and failure rate.
 13. Themethod of claim 9, further comprising: selecting an instance of abusiness service asset located by the executed search; and negotiating aworkflow with an owner of the returned business service asset tofacilitate asset use.
 14. The method of claim 13, wherein asset usecomprises developing a business process application.
 15. The method ofclaim 9, wherein business service categories within the processdimension comprise: Pre-Order and Sales Order Management; Product,Pricing, Inventory Management; Supplier, Partner Management;Provisioning, Activation, Field Fulfillment Management; Financial andAsset Management; Customer, Workforce Management; Device, ElementManagement; Trouble, Test, Fault, Measurement Management Billing,Payment, Mediation, Fraud, Credit Management; Communication ProcessManagement—Transmission, Routing, Signaling, Switching, State/Session;and General, Middleware Management—Distribution, Performance, Security,Logging, Alarms; wherein business service categories within the payloaddimension comprise: Quotation; Order or Service Request; Order Status(includes Fulfillment, Acknowledgement); Network Service Record;Customer Service Record; Work Order; Credit Status; Bill (includesInvoice); Payment; Usage; Trouble Ticket; Circuit Detail; Product;Receipt; Person (workforce or customer identity); Equipment; Document(Standard MIME types exchanged in payload); and Request (transaction,process); wherein business service categories within the productdimension comprise: Local Services; Access Services; Long DistanceServices; DSL Services; Broadband/Optical Transport Services;Video/Gaming Services; Centrex and PBX Services; Internet Services;Equipment Services (CPE/Switches/Parts) Directory Services; Convergenceand Collaboration Services; VOIP Services; Content Storage andDistribution Services (Email, Fax, Pager, File Transfer, etc.); WirelessServices; Security Services; and Special Services.
 16. A system,comprising: at least one database system for housing one or morebusiness service assets; at least one server computer in communicationwith the at least one database system; and a computer program product,responsive to a request by one or more user computers, the computerprogram product comprising a non-transitory computer readable mediumhaving stored thereon computer readable code for causing publishing anddiscovering of the business service assets in a network, the computerreadable program code comprising: computer readable program code forstructuring a framework comprising a multi-dimensional businessprocess-oriented taxonomy, the taxonomy comprising one or more businessservice categories within a process dimension, a payload dimension, anda product dimension; computer readable program code for publishing abusiness service asset to the framework, the publishing being responsiveto: a first user selecting from within an interface at least one of theone or more business service categories to associate with the businessservice asset, and a second user screening the business service asset toensure that the business service asset meets organizational criteria;and computer readable program code for discovering the business serviceasset within the framework, the discovering being responsive to a thirduser's selection of the at least one of the one or more business servicecategories within the at least one dimension of the multi-dimensionalbusiness process-oriented taxonomy, the business service categoriesbeing in alignment with the business service asset.
 17. The system ofclaim 16, wherein one or more of the at least one database system iscontained within one or more of the at least one server, the databasesystem being responsive to interactions with the computer programproduct.
 18. The system of claim 16, wherein each database systemcomprises a computer data structure stored in a memory of a computerconfigured to manipulate the data structure, the computer beingresponsive to interactions with the computer program product.
 19. Thesystem of claim 16, wherein the computer program product is configuredto operate on the at least one server computer.
 20. The system of claim16, wherein the computer program product is configured to operate on theone or more user computers.
 21. An interface comprising a non-transitorycomputer readable medium having stored thereon computer readable programcode for publishing and discovering business service assets within anetwork system, the interface comprising: for publishing a businessservice asset: receiving from a publisher a business service asset witha request for publication of the business service asset and selectionfrom within a first interface of one or more business service categoriesin alignment with the business service asset, the business servicecategories forming a multi-dimensional business process-orientedtaxonomy within a framework; in response to the request for publicationof the business service asset, screening the business service asset by ascreener and, if qualified, publishing the business service asset;returning to the publisher acknowledgement that the business serviceasset has been published or denied; and for discovering the businessservice asset: receiving from a discoverer a user selection from withina second interface of one or more business service categories formingthe multi-dimensional business process-oriented taxonomy within theframework, and a request to locate the business service asset inalignment with the selected categories; returning to the discoverer aninstance of the business service asset located, wherein themulti-dimensional business process-oriented taxonomy comprise a processdimension, a payload dimension, and a product dimension.
 22. Theinterface of claim 21, wherein each of the first and second interfacescomprises a graphical user interface.
 23. The interface of claim 21,wherein each of the first and second interfaces comprises aprogram-to-program interface.